NTISthis.com

Evidence Guide: ICTSAS504 - Develop and conduct client acceptance test

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS504 - Develop and conduct client acceptance test

What evidence can you provide to prove your understanding of each of the following citeria?

Identify acceptance criteria and develop test plan

  1. Review system requirements documentation and project plans to identify mandatory system objectives and optional criteria, and conditions for system acceptance
  2. Develop test plan based on system requirements
  3. Review and validate test plan based on mandatory criteria, conditions, and system objectives and requirements
  4. Communicate test plan to client and prepare client for acceptance test
  5. Notify appropriate person of the scheduled acceptance test
Review system requirements documentation and project plans to identify mandatory system objectives and optional criteria, and conditions for system acceptance

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop test plan based on system requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review and validate test plan based on mandatory criteria, conditions, and system objectives and requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Communicate test plan to client and prepare client for acceptance test

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Notify appropriate person of the scheduled acceptance test

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Perform functional testing on software modules

  1. Prepare test environment for client use
  2. Perform testing according to test plan and documentation
  3. Execute each test cycle
  4. Document errors, difficulties and problems
Prepare test environment for client use

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Perform testing according to test plan and documentation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Execute each test cycle

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document errors, difficulties and problems

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Validate test results against expected results

  1. Record and investigate discrepancies and corrections according to project procedures and timeframe
  2. Brief client on outcomes to ensure client understands test results
  3. Monitor system performance as required
  4. Reschedule required code changes or modifications
Record and investigate discrepancies and corrections according to project procedures and timeframe

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Brief client on outcomes to ensure client understands test results

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Monitor system performance as required

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Reschedule required code changes or modifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Obtain sign-off and acceptance

  1. Confirm test results with client
  2. Identify and document client concerns over system operation
  3. Identify possible solutions to concerns and notify appropriate development staff as required
  4. Confirm client approval and obtain sign-off
  5. Seek and formalise agreement of involved parties regarding the rescheduling of further required maintenance
Confirm test results with client

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify and document client concerns over system operation

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify possible solutions to concerns and notify appropriate development staff as required

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Confirm client approval and obtain sign-off

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Seek and formalise agreement of involved parties regarding the rescheduling of further required maintenance

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify acceptance criteria and develop test plan

1.1 Review system requirements documentation and project plans to identify mandatory system objectives and optional criteria, and conditions for system acceptance

1.2 Develop test plan based on system requirements

1.3 Review and validate test plan based on mandatory criteria, conditions, and system objectives and requirements

1.4 Communicate test plan to client and prepare client for acceptance test

1.5 Notify appropriate person of the scheduled acceptance test

2. Perform functional testing on software modules

2.1 Prepare test environment for client use

2.2 Perform testing according to test plan and documentation

2.3 Execute each test cycle

2.4 Document errors, difficulties and problems

3. Validate test results against expected results

3.1 Record and investigate discrepancies and corrections according to project procedures and timeframe

3.2 Brief client on outcomes to ensure client understands test results

3.3 Monitor system performance as required

3.4 Reschedule required code changes or modifications

4. Obtain sign-off and acceptance

4.1 Confirm test results with client

4.2 Identify and document client concerns over system operation

4.3 Identify possible solutions to concerns and notify appropriate development staff as required

4.4 Confirm client approval and obtain sign-off

4.5 Seek and formalise agreement of involved parties regarding the rescheduling of further required maintenance

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify acceptance criteria and develop test plan

1.1 Review system requirements documentation and project plans to identify mandatory system objectives and optional criteria, and conditions for system acceptance

1.2 Develop test plan based on system requirements

1.3 Review and validate test plan based on mandatory criteria, conditions, and system objectives and requirements

1.4 Communicate test plan to client and prepare client for acceptance test

1.5 Notify appropriate person of the scheduled acceptance test

2. Perform functional testing on software modules

2.1 Prepare test environment for client use

2.2 Perform testing according to test plan and documentation

2.3 Execute each test cycle

2.4 Document errors, difficulties and problems

3. Validate test results against expected results

3.1 Record and investigate discrepancies and corrections according to project procedures and timeframe

3.2 Brief client on outcomes to ensure client understands test results

3.3 Monitor system performance as required

3.4 Reschedule required code changes or modifications

4. Obtain sign-off and acceptance

4.1 Confirm test results with client

4.2 Identify and document client concerns over system operation

4.3 Identify possible solutions to concerns and notify appropriate development staff as required

4.4 Confirm client approval and obtain sign-off

4.5 Seek and formalise agreement of involved parties regarding the rescheduling of further required maintenance

Evidence of the ability to:

develop a test plan based on system requirements and acceptance criteria

undertake functional testing

validate results and obtain client sign-off acceptance.

Note: Evidence must be provided on at least TWO systems.

To complete the unit requirements safely and effectively, the individual must:

compare and contrast the key features and processes of automated test tools

analyse key aspects of business rules and standards

discuss client user requirements

analyse the system or application being tested

describe a range of testing techniques.